Adaptable Project Management – A combination of Agile and Project Management for All (PM4A) by Colin Bentley

Author:Colin Bentley [Colin Bentley]
Language: eng
Format: epub
Publisher: IT Governance Publishing
Published: 2020-08-24T16:00:00+00:00

Copy holders and potential users Details of who holds a copy of the product plus who may require a copy when the product reaches a certain status.

Project issue cross reference If this version of the product has been caused by an issue, this should be cross-referenced as an audit trail.

Correspondence cross reference A reference to any relevant correspondence that affects this product or version of it.

8.4.1.5 Baselines

Baselines are moments in a product’s evolution when it and all its components have reached an acceptable state, such that they can be ‘frozen’ and used as a base for the next step. The next step may be to release the product to the customer, or it may be that you have ‘frozen’ a design and will now construct the products.

Products constantly evolve and are subject to change as a project moves through its life cycle and, later, in the operational life of the product. A development team will need to know the answer to many questions, such as:

•What is the latest agreed level of specification to which we are working?

•What exact design are we implementing?

•What did we release to site X last January?

In other words, a baseline is a frozen picture of what products and what versions of them constituted a certain situation. A baseline may be defined as a set of known and agreed configuration items under change control from which further progress can be charted. This description indicates that you will only baseline products that represent either the entire product or at least a significant product.

A baseline is created for one of several reasons:

•To provide a sound base for future work.

•As a point to which you can retreat if development goes wrong.

•As an indication of the component and version numbers of a release.

•As a bill of material showing the variants released to a specific site.

•To copy the products and documentation at the current baseline to all remote sites.

•To represent a standard configuration (e.g. product description) against which supplies can be obtained (e.g. purchase of personal computers for a group).

•To indicate the state the product must reach before it can be released or upgraded.

•As a comparison of one baseline against another in terms of the products contained and their versions.

•To transfer configuration items to another library, e.g. from development to production, from the supplier to the customer at the end of the project.

The baseline record itself should be a product so that it can be controlled in the same way as other products. It is a baseline identifier, date, reason and list of all the products and their version numbers that comprise that baseline. Because of its different format it is often held in a separate file.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.